System for maintaining imaging device accounting data

ABSTRACT

A system is provided for maintaining imaging device (IDev) accounting data. A primary accounting server (PAS) sends messages to an imaging device (IDev) and to a lightweight accounting back-up server (LABS). The PAS receives messages from the IDev and updates a primary IDev activity log (PIAL). The IDev receives messages from the Primary server and a LABS in communication with the IDev. The LABS sends and receives messages and data from the IDev and from the PAS. The IDev sends a record of its activity to the PAS when the PAS is available, and the PAS maintains a primary IDev activity log (PIAL). The IDev sends a record of its activity to the LABS when the PAS is not available and the LABs maintains a temporary IDev activity log (TIAL). The PAS updates the PIAL with the TIAL data after a period of unavailability.

RELATED REFERENCES

This application is a Divisional of U.S. patent application Ser. No.11/192,865, entitled “Methods and Systems for Imaging Device AccountingData Maintenance”, filed Jul. 29, 2005 now U.S. Pat. No. 8,023,130,which is a continuation-in-part of U.S. patent application Ser. No.10/962,248, entitled “Methods and Systems for Imaging Device RemoteApplication Interaction, filed on Oct. 8, 2004 now U.S. Pat. No.8,018,610; U.S. patent application Ser. No. 11/192,865 is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,793,entitled “Methods and Systems for Imaging Device Remote Form Management,filed on Oct. 8, 2004 now U.S. Pat. No. 8,035,831; U.S. patentapplication Ser. No. 11/192,865 is also a continuation-in-part of U.S.patent application Ser. No. 10/961,911, entitled “Methods and Systemsfor Imaging Device Remote Location Functions, filed on Oct. 8, 2004;U.S. patent application Ser. No. 11/192,865 is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,594,entitled “Methods and Systems for Imaging Device Remote documentManagement, filed on Oct. 8, 2004; and U.S. patent application Ser. No.11/192,865 is also a continuation-in-part of U.S. patent applicationSer. No. 10/962,103, entitled “Methods and Systems for Imaging DeviceDocument Translation, filed on Oct. 8, 2004 now U.S. Pat. No. 7,969,596;U.S. patent application Ser. No. 11/192,865 also claims the benefit ofU.S. Provisional Patent Application No. 60/707,066, entitled “Methodsand Systems for Imaging Device Applications,” filed Jul. 28, 2005.

FIELD OF THE INVENTION

Embodiments of the present invention comprise methods and systems forpreserving imaging device (IDev) accounting data when an imagingsystem's main accounting server becomes unavailable.

BACKGROUND

Imaging devices such as printers, copiers, scanners and fax machines canhave a wide array of functions and capabilities to fit specific uses orcombinations of uses. Imaging, devices often take the form of amulti-function peripheral device (MFP) that combines the functions oftwo or more of the traditionally separated imaging devices. An MFP maycombine any number of imaging devices, but typically comprises thefunctions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storageand processing such as processors, hard disk drives, memory and otherdevices. As imaging devices add more features and functions, they becomemore costly and complex.

More complex imaging devices and MFPs may comprise network connectivityto provide communication with other computing devices, such as personalcomputers, other

imaging devices, network servers and other apparatus. This connectivityallows the imaging device to utilize off-board resources that areavailable on a connected network.

Imaging devices typically have a user input panel with an array ofbuttons, knobs and other user input devices. Some devices also have adisplay panel, which can be for display only or can be a touch paneldisplay that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged incooperation with the display can display menu data that may be selectedby user input. This menu data is typically driven by an on-board servermodule within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention comprise methods and system's forthe continuous capture of accounting data when an imaging system's mainaccounting server becomes unavailable.

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprisingan imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using amarkup language;

FIG. 6 shows an exemplary, remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computingdevice;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device methodusing a markup language;

FIG. 10 is a diagram showing a system comprising multiple imagingdevices in connection with a remote computing device;

FIG. 11 is a chart showing steps of a method comprising RCD processingof user input data;

FIG. 12 is a diagram showing components of some embodiments comprisinglinked resources;

FIG. 13A is a diagram showing an exemplary system comprising IDevs,computing devices, a primary accounting server, and LABSs;

FIG. 13B is a diagram showing an exemplary system comprising an IDev, acomputing device comprising a LABS and a primary accounting server;

FIG. 14A is a chart showing the steps of a method of some embodimentscomprising maintenance of IDev activity data in the event of a primaryaccounting server failure;

FIG. 14B is a chart showing the steps of a method of some embodimentscomprising recovering temporary IDev activity data after a primaryaccounting server is put back into service;

FIG. 15 is a chart showing the steps of a method of some embodimentscomprising finding a LABS when a primary accounting server fails;

FIG. 16 is a chart showing the steps of a method of some embodimentscomprising finding a new LABS when a current LABS fails;

FIG. 17 is a chart showing the steps of a method of some embodimentscomprising recovering temporary IDev activity data after a primaryaccounting server is put back into service; and

FIG. 18 is a chart showing the steps of a method of some embodimentscomprising recovering temporary IDev activity data after a primaryaccounting server is put back into service.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Embodiments of the present invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The figures listed above are expressly incorporatedas part of this detailed description.

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the methods and systems of the present invention is notintended to limit the scope of the invention but it is merelyrepresentative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied inhardware, firmware and/or software. While exemplary embodiments revealedherein may only describe one of these forms, it is to be understood thatone skilled in the art would be able to effectuate these elements in anyof these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces andarchitecture that integrate imaging devices with remote computing deviceapplications and environments to provide solutions that may not bepossible solely with an imaging device alone. Some embodiments comprisean infrastructure and set of interfaces that allow applications on anetwork to programmatically control imaging device functions andinteract with a user through an imaging device input panel. Softwarefunctions that are not practical within the imaging device can beperformed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device(IDev) may be described as a device that performs an imaging function.Imaging functions comprise scanning, printing, copying, imagetransmission (sending and receiving), image conversion and otherfunctions. Exemplary imaging devices comprise printers, copiers,facsimile machines, scanners, computing devices that transmit, convertor process images and other devices. An IDev may also perform multipleimaging functions. For example, and not by way of limitation, amulti-function peripheral device (MET), which typically has thecapability to perform a plurality of functions comprising a printer,scanner, copier and/or a facsimile machine or imagetransmitter/receiver, is a type of imaging device. Other MFP imagingdevices may comprise other combinations of functions and still qualifyas an IDev.

For the purposes of this specification and claims, a remote computingdevice (RCD) is a device capable of processing data and communicatingwith other devices through a communications link. An RCD is a remotedevice because it requires a communications link, such as a networkconnection, a telephone line, a serial cable or some other wired orwireless link to communicate with other devices such as an imagingdevice. Some exemplary RCDs are network servers, networked computers andother processing and storage devices that have communications links.

Some embodiments of the present invention may be described withreference to FIGS. 1 & 2. These embodiments comprise an imaging device(IDev) 4 that may be a multi-function peripheral device (MFP) or asingle function device. The imaging device 4 further comprises a userinterface (UI) panel 2, which may comprise input buttons 14 and adisplay device 12 or may comprise a touch panel system with or withoutbuttons 14. User input and display may also be performed through aseparate UI device 8, which may be connected to the imaging device 4 bya communication link 12, such as a USB connection, a network cable, awireless connection or some other communications link. UI device 8 maycomprise an input device, such as a keyboard or buttons as well as adisplay device, which may also be a touch screen panel. UI device 8 mayalso comprise an interface for transfer of instructions that are inputto the device 8 from a remote input device. This form of UI device 8 maycomprise memory sticks, USB memory cards and other storage devices thatmay be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6that is linked to the imaging device 4 via a communications link 10,such as a network connection. This network connection may be a typicalwired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD6 to the imaging device UI panel 2 or remote panel 8 via the networkconnection 10. Once this menu data is fed to the imaging device 4, an UIpanel 2, 8 on the imaging device 4 may be used to interact withapplications that run on the remote computing device 6. User inputreceived from UI panels 2, 8 may be returned directly to the remotecomputing device 6.

A Web Service is a software application identified by a Uniform ResourceIdentifier (URI), whose interfaces and binding are capable of beingdefined, described and discovered by Extensible Markup Language (XML)artifacts and supports direct interactions with other softwareapplications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more WebServices to control various features in the imaging device 4, such asenabling, disabling or setting device values or controlling devicefunctions.

Embodiments of the present invention allow network applications runningon remote computing devices to interact with the user of the imagingdevice through the imaging device I/O panel. These embodiments allowimaging device user interface (UI) control (i.e., touch panel,button/display) by applications. Some embodiments may also integratecustom display screens or menus with the native imaging device UI.Embodiments may hand off control of imaging device functions betweenstandard operation modes performed on the imaging device in response touser input to an imaging device UI and open systems modes that utilizenetwork resources, such as applications on RCDs, through user input atthe imaging device UI.

Embodiments of the present invention comprise network-based applicationsthat have full control over the imaging device UI to display text andgraphics in any format. In these embodiments, the application canprogrammatically display buttons, textboxes, graphics, etc. in anylayout desired.

In some embodiments, the UI layout is easy to program using a standardlanguage, such as a markup language. These languages comprise HypertextMarkup Language (HTML), Extensible Markup Language (XML), WirelessMarkup Language (WML), Extensible Hypertext Markup Language (XHTML) andother languages.

In some embodiments of the present invention a remote computing deviceapplication or server application is able to request a keyboard UI to bedisplayed on the imaging device display 12, 8. In some embodiments, thisfunctionality is available on the imaging device and does not need to berecreated by remote computing device applications. In some embodiments,the remote computing device may define the keyboard prompt and defaultvalues. These embodiments may comprise a remote computing device that isable to rename imaging device UI buttons, such as the OK and Cancelbuttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging deviceUI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remotecomputing device application that is registered as the ExternalAuthorization server. The External Authorization application may controlaccess to the imaging device and may have top-level control of the UI.UI control may be given to this application in the same manner thatcontrol is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks tosee if an External Authorization application is registered. If so, theimaging device is placed in disabled mode and the application iscontacted to take control of the UI. If the External Authorizationserver is not available, an error message may be displayed and thedevice may remain disabled. The imaging device may periodically try tocontact the External Authorization server until it is available, Table 1below describes what entity has control of the UI, in an exemplaryembodiment, when the device is in a disabled state.

TABLE 1 UI Control in Disabled State Button Press UI Control IndicatorLights Device boots External Application None Document Filing ExternalApplication None Image Send External Application None Copy ExternalApplication None Job Status Device - standard Job Status Job Statusscreens Custom Settings Device - standard Custom Settings N/A screens OSMode Not available when device is disabledRemote Computing Device Applications

In embodiments of the present invention, access to the custom UI panelsof imaging devices may vary from application to application. Somesolutions, such as Document Management integration, may wish to leveragethe native Image Send screens, but display some custom UI's to gatheradditional information about a scan job. Other solutions, like customprinting applications, may be accessed from a separate mode than thenative functions.

In order to accommodate the diversified needs of these solutionsapplications, embodiments may support multiple integration points for UIcontrol. These integration points are based on a user action (“trigger”)for which applications may register. In some embodiments, applicationsmay be registered with target devices so that the device knows that when“trigger A” occurs on the front panel to contact “remote computingdevice B” for instructions. In exemplary embodiments, applications maybe integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function andcontacted when that function's hardware key is pressed (e.g. Image Send)on the imaging device UI. Any UI information provided by the remotecomputing device may be displayed instead of the standard functionscreens native to the imaging device. This trigger may be used forapplications that wish to replace the existing functions with completelycustom UI's, such as an alternative scan solution or a specializeddisplay, such as a “Section 508” compatible screen or otherspecialized-need interface that may have large buttons or otheraccommodations.

In some embodiments, each function on the imaging device may have a menuon the touch screen that remote computing devices, such as servers, canregister. This enables solutions applications to provide custom contentand still use some of the standard functionality provided by the imagingdevice. When a button assigned to a custom application is selected, amenu will be displayed with the solutions registered to that function.Users may select the desired solution and the remote computing devicewill be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remotecomputing device application access can be accessed from the job queueportion of the UI that is displayed on every screen. This trigger pointmay be used for applications that do not fit within one of the standarddevice functions, such as custom printing solutions on an imagingdevice. When the RCD menu is selected, a menu will be displayed with thesolutions applications registered to the generic RCD mode. Users willselect the desired solution and the remote computing device will becontacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device isenabled, additional hardware keys may be used to manage the device.Hardware key assignments for an exemplary embodiment are shown in table2.

TABLE 2 Exemplary Hardware Key Assignments Button Press Standard IDevMode RCD Mode Mode keys (Copy, Clear current job Clear current jobsettings, Doc Filing, Image settings, move to move to target screenSend) and Custom target screen Settings key Job Status key Move to JobStatus, Move to Job Status, maintain current maintain current settings &settings & UI UI location location Clear (C) Clears settings Sends clearevent to external application Clear All (CA) Clears settings, cancelsCancels job and returns to job, and returns to default IDev screendefault IDev screen (notification sent to external application) **WhenExternal Authorization is controlling the UI, only notification is sentStart Initiates scan function Initiates scan function Number keys Inputfor copy count or Not used fax numbers * Logs user out (disable Logsuser out (disable device and contact device and contact ExternalExternal Authorization Authorization for screens) for screens)

In some embodiments, in addition to the * key for logout, a timeoutperiod may be implemented. Some embodiments also comprise an auto clearsetting that can be configured for a given period of time, such as 10 to240 seconds (or disabled). In these embodiments, when there is noactivity for the time configured in auto clear, the device mayautomatically return to disabled mode and attempt to contact a remotecomputing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing deviceapplication may have full or only partial control of the imaging deviceUI and a particular imaging job. In some embodiments, partial controlmay include cases where a remote computing device is monitoring clicks,but native modes are responsible for the UI interaction and controllingthe job. Partial control may also include cases where the remotecomputing device application is integrated with a native mode (UItrigger=function custom menu). In these embodiments, the imaging devicemay handle all error and jam notifications with only a notification sentto the relevant remote computing device application.

For some embodiments, in cases where the remote computing deviceapplication has full control over the UI and the job, error and jamnotifications may be handled differently depending on the type of error.For recoverable errors, a notification may be sent to the remotecomputing device application and the application may be responsible fordisplaying messages and resolving the error. For non-recoverable errors,the imaging device and RCD mode may interact to gracefully handle theerror condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job,several applications may need control over an imaging device including,but not limited to, an External Authorization application, a standardRCD application, an imaging device native mode and other applications.The following section describes, for an exemplary embodiment, thevarious steps in an exemplary job, the entities that may have controlduring each step, and what type of control may be allowed.

Step 1: User provides credentials to access the device at the device UI.This step may be controlled by a remote computing device, such as anExternal Authorization application or by Internal Accounting (nativemode) in the imaging device itself. At the end of this step, the deviceis enabled. The External Authorization application may also specifydefault parameters or disable specific job parameters (e.g. default fileformat is PDF, but user may change; color mode is set to B/W and usermay not change).

Step 2: User sets parameters for the job using one of the native imagingdevice modes or a standard RCD application. At the end of this step theuser makes an input to initiate the job. When the input is made, anoptional notification may be sent to the standard RCD application, whichcan then change job parameters if desired. An e-mail application is oneexample of an application that may request notification when the userinput is made. A user may use native Image Send screens or other inputto select scan options and choose e-mail recipients. A user may thenselect a custom application button and choose the scan-to-e-mail optionfrom the menu. The e-mail application may then display custom screensfor the user to set permissions for the file. Once a user places theoriginal document(s) on the scanner and initiates the process, thee-mail application may capture the destination parameters set by theuser and change the target destination to the e-mail application FTPserver. The e-mail application may then receive the file, apply theappropriate permissions, and send to the e-mail recipients selected bythe user. A remote computing device application may also want to retakecontrol of the UI at this point, if, as in some embodiments, theapplication generates thumbnails of the scanned images and displays themto the user for verification.

Step 3: Once the job is initiated, the imaging device is responsible forscanning or RIPing the job and spooling it to the HDD. If the imagingdevice is configured to authorize jobs with an external authorizationapplication, it may send a click report to the application and wait forinstructions. The external authorization application may enable the jobfor sending/printing, cancel the job, or change job parameters (and thenenable). As an example, a rules-based printing application may wish tochange job parameters after it receives a click report. Some rules-basedprinting applications support rules-based printing and scanning that canlimit what each user is allowed to do based on the time of day, thedestination, or many other parameters. For example, only users in themarketing group may be able to scan high-quality color images. If a userfrom another group selects color and 600 dpi, a rules-based applicationmay change the parameters to color and 200 dpi. At the end of this stepthe job should either be authorized or canceled.

Step 4: In some embodiments, this may be an optional step, where thestandard RCD application in step 2 may have specified the destination asa HDD for temporary storage. This step may also be used, in someembodiments, by a Java application running on the imaging device. Forexample, a government office may have a custom encryption applicationrunning on the device that takes the scanned document, encrypts it, andthen requests the imaging device to send it to the target destinationselected by the user in step 2. In some embodiments, it may bebeneficial to send a notification to the external authorizationapplication after this step—because the imaging device does not know howlong the file will be on the HDD or what the application is going to dowith it and after the send/print step.

Step 5: In the final step, the file is actually output. In typicalembodiments, the file is either sent over the network or printedlocally. At the end of this step, a notification that the job wassuccessfully completed should be sent to the external authorizationapplication and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application tocontrol access to an imaging device for vend applications and to managethe device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and VendAPI allows applications to enable and disable access to the device andtrack click counts. The Device Control and Vend API may provide an RCDwith the following controls:

Enable/disable device of function—this may allow an RCD to enable ordisable access to the device as a whole or by function to enforceindividual user privileges. In some exemplary embodiments, the functionslisted in Table 3 may be selectively enabled or disabled by anapplication.

TABLE 3 Device Functions Enable/Disable Description Copy Copy function(Copy button) Image Send Scan and fax function, plus send from DocFiling (Image Send button) Document Filing All access to Document Filingfunctions (Document Filing button) Print Network prints, pull print fromfront panel, and print from Document Filing (No button control)

Report clicks used at the end of a successful job, the clicks used maybe reported back to an RCD including:

TABLE 4 Job and Page Characteristics Fax PC- E-mail/ Scan Item CopyPrint Send Fax FTP Broadcast to HD JOB Characteristics Job Mode Yes YesYes Yes Yes Yes Yes Broadcast No No Yes Yes Yes Yes No Manage No. UserName Yes Yes Yes Yes Yes Yes Yes Address No No Yes Yes Yes # No StartTime Yes Yes Yes Yes Yes Yes Yes End Time Yes Yes Yes Yes Yes Yes YesTotal Page Yes Yes Yes Yes Yes Yes Yes Result Yes Yes Yes Yes Yes YesYes Error Cause No No Yes Yes Yes Yes No Doc Filing Yes Yes Yes Yes YesYes Yes Save Mode *1 *1 *1 *1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1Yes File Size Yes Yes *1 *1 *1 *1 Yes Resolution Yes Yes Yes Yes Yes YesYes Special Yes Yes Yes No Yes Yes Yes Finishing Yes Yes No No No No NoFile Format No No No No Yes Yes No Compression No No No No Yes Yes NoPAGE Characteristics Copy Yes Yes Yes Yes Yes # Yes Paper Size Yes YesYes Yes Yes Yes Yes Simplex/ Yes Yes Yes Yes Yes Yes Yes duplex PaperType Yes Yes Yes Yes No No Yes Page Yes Yes Yes Yes Yes Yes Yes *1 - Yeswhen Document Filing is used

Debit mode—in these embodiments, when an application enables the deviceit may specify if the current job requires authorization. If so, the jobwill be spooled to memory and click information (e.g., as defined inTable 4) will be sent to an RCD. An RCD will then notify the device ifthe job should be deleted or output/sent. At this point, the applicationalso has the option of changing job parameters. If the application doesnot require authorization, the job will continue as normal and a clickreport will be sent at the end of the job.

Print job accounting—in these embodiments, an RCD may wish to monitorprint jobs along with walk-up functions. For print job accounting, anIDev may monitor all incoming print jobs and send accounting data in thePJL header to an RCD for verification before printing the job. The RCDwill evaluate the accounting data (or lack thereof) and inform the IDevto continue with or cancel the job.

Report on unidentified jobs—in these embodiments, an RCD may also wishto monitor print jobs that it cannot associate to a specific user, suchas device reports and incoming fax jobs. The RCD can register to receiveclick counts for all unidentified jobs, so that it may bill them to ageneral account.

Device Management API

In some embodiments of the present invention, a Device Management APIallows a network application to remotely setup and manage the imagingdevice. In exemplary embodiments, the Device Management API may providean RCD with the following controls:

-   -   Device status—an RCD may request the current status of the        device. This is the same status information as reported on the        embedded web pages.    -   Device configuration—an RCD can retrieve a list of installed        options supported by the device,    -   Web Page settings—an RCD application can retrieve and set any of        the values that are configurable on the embedded web pages.    -   Key Operator Programs—an RCD application can retrieve and set        any of the values that are configurable in Key Operator        Programs, including software keys.    -   Custom Settings—an RCD application can retrieve and set any of        the values that are configurable in Custom Settings.    -   Job Status—an RCD application can retrieve the current job queue        and history information and reprioritize or delete jobs in the        queue.    -   Click counts—an RCD application can retrieve device total counts        and clicks for each function by account code.    -   Data Security settings—an RCD application may retrieve the        status information on the DSK (e.g. last erase) and initiate        data clear functions.    -   RED data—an RCD can retrieve all data typically sent in a RED        message.    -   Remote reboot—an RCD can initiate a reboot of the imaging        device.

The above groupings are provided only as an exemplary embodimentdetailing which settings should be included. In some embodiments, actualAPI's should be grouped by functional areas since there may be overlapbetween Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remotecomputing device application to configure internal accounting and reportclick counts. In some exemplary embodiments an Internal Accounting APImay include:

-   -   Set Auditing Options—an RCD may set auditing options including        which modes auditing is enabled for, “account number security”,        and “cancel jobs of invalid accounts.”    -   Manage Account Codes—an RCD can add, edit, or delete account        codes    -   Account Limits—an RCD application can specify a maximum number        of clicks by function for individual account codes or for all        account codes    -   Account Reset—an RCD application can reset the click count for        an individual account or for all accounts    -   Retrieve Clicks—an RCD can retrieve the number of clicks by        function for each account code        Font and Form Management API

Some embodiments of the present invention may comprise a Font and FormManagement API, which allows an RCD application to remotely download andmanage fonts and forms in mass-storage. In some exemplary embodiments, aFont and Form Management API may provide a remote computing device withthe following controls:

-   -   Mass storage control—an RCD application can retrieve mass        storage status information including storage capacity, space        available, and write-protect mode plus modify write-protect        status.    -   Resource list—an RCD application can retrieve a list of stored        fonts and forms including font or macro ID, font number,        font/form name, escape sequence, and file size.    -   Download resource—an RCD application can download PCL fonts, Pa,        macros, and PS fonts and forms. Any special processing that is        performed when a resource is downloaded via the web pages will        also be performed when the resource is downloaded via Open        Systems.    -   Delete resource—an RCD application can delete any resource        stored in mass storage,    -   Upload resources—an RCD application can upload an individual or        all resources. On devices where effective memory management is        unavailable, a server application can use this function to        “defrag” mass storage.    -   Font/macro ID's—an RCD application can assign or modify the ID's        assigned to PGL fonts and macros.        Firmware Management API

In some embodiments of the present invention, a Firmware Management APImay allow a remote computing device or network application to remotelydownload and manage the imaging device firmware. In some exemplaryembodiments, a Firmware Management API may provide a remote computingdevice (e.g., a server) with the following controls:

-   -   Firmware versions—an RCD application can retrieve the current        firmware version numbers.    -   Service mode—an RCD application can place the MEP in service        mode to lockout other jobs that will interfere with firmware        upgrade. Upon receiving a service mode request, the IDev will        stop accepting incoming jobs, complete all jobs in the queue,        and then notify the server that it is in service mode.    -   Update firmware—an RCD can download an updated firmware version        to the device. If a reboot is necessary, the IDev will perform        it automatically when download is complete.    -   Download status—the IDev will send a status notification        (success/error) to an RCD after firmware download.    -   Revert to previous version—if firmware update is not successful,        the application can request the IDev to revert to the previous        firmware version.

DEVICE FUNCTION API'S

in some embodiments of the present invention, device function API'sallow a remote computing device application to use existing imagingdevice functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computingdevice application with the following controls:

-   -   Image Send Parameters—a remote computing device application can        get and set values for the following scan and fax parameters:        -   COLOR OR B/W        -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL        -   RESOLUTION        -   FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE        -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB            BUILD        -   FILENAME        -   SUBJECT        -   MESSAGE        -   SENDER        -   SCHEDULE SEND TIME        -   PAGE DIVISION (BOOK SCANNING)        -   COVER PAGE        -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)        -   THIN PAPER SCANNING        -   DESTINATION        -   DOCUMENT FILING    -   Initiate Scan—the remote computing device application can        initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if scanparameters may be modified by the user or not. If one remote computingdevice application (e.g. Access Control) specifies that a parametercannot be changed and then a second application (e.g. DocumentManagement) tries to set the parameter, a notification may be sent tothe second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computingdevice applications using standard printing channels. In some exemplaryembodiments, a Print API may provide a remote computing device with thefollowing additional control:

-   -   PJL sniffing—an RCD application can register with the IDev to be        contacted for instructions when a specific PJL command is found        in a print job. The RCD can then instruct the IDev to replace        the command, cancel the job, or continue printing. This        interface may be used in applications like accounting and        other-brand compatibility.        Copy API

In some embodiments of the present invention, a Copy API may provide aremote computing device with the following exemplary controls:

-   -   Copy Parameters—an RCD application can get and set values for        the following copy parameters:        -   COLOR OR B/W        -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE            LEVEL        -   PAPER SELECT (BY TRAY)        -   COPY RATIO        -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2TO1; BINDING EDGE        -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFFSET        -   ORIGINAL SIZE        -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.        -   DOCUMENT FILING    -   Initiate Copy—an RCD application can initiate the copy function        (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if copyparameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API mayprovide a remote computing device with the following exemplar),controls:

-   -   Backup/restore—the remote computing device application can        import and export a batch file with all Document Filing data. In        some embodiments, this package will be in a proprietary format        since it contains documents that are password-protected and        should not be accessed individually this is typically for        restore in case of failure or cloning to other devices.    -   File/folder list—the remote computing device application can        retrieve, modify, and create new files and folders to be stored        on the IDev (also covered in device management).    -   Download file—the remote computing device can download a new        file to the Document Filing systems and specify folder,        filename, username, and password,    -   User list—the remote computing device application can retrieve,        modify, and create new users to be stored on the IDev (also        covered in device management).    -   HDD Status—the remote computing device application can retrieve        the current HDD status including the % allocated to the main        folder, quick folder, and custom folders and the % remaining.    -   Doc Filing Parameters—the remote computing device application        can get and set values for storing a file to Doc Filing        including:        -   EXPOSURE        -   RESOLUTION        -   ORIGINAL—SIZE, SIMPLEX/DUPLEX        -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,            PASSWORD        -   SPECIAL MODES—ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD            SHOT    -   Initiate Print—the remote computing device application can        select a stored file and initiate a print including the        following parameters:        -   PAPER SIZE/SOURCE        -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET        -   SIMPLEX/DUPLEX (TABLET/BOOKLET)        -   TANDEM PRINT        -   NUMBER OF COPIES        -   DELETE OR STORE AFTER PRINTING    -   Initiate Send—the remote computing device application can select        a stored file and initiate a send including the following        parameters:        -   RESOLUTION        -   FILE FORMAT        -   DESTINATION        -   TIMER        -   SENDER        -   FILENAME        -   SUBJECT        -   MESSAGE

SECURITY

Allowing external applications to control an imaging device opens up theimaging device to new security vulnerabilities. In embodiments of thepresent invention that provide some security measures, the followingexemplary items are security concerns that may be addressed by theremote computing device interface.

Access to remote computing device interfaces may be limited to validapplications. Embodiments provide extensive access and control of theimaging device, which poses a significant security risk. The interfaceof these embodiments may be protected from access by attackers, whilemaintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protectedduring network transfer. User credentials and job data may be securedduring network transfer to ensure that it cannot be stolen, an intrudercannot monitor device activity, and a man-in-the-middle attack cannotchange messages. Imaging devices may support Secure Sockets Layer (SSL)and other connections to ensure data is safe white being communicatedbetween the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access.For users with strict security policies, administrators may have theability to disable access by remote computing devices or limit access tospecific applications. Administrators may have an option to register thelimited applications that they wish to access the imaging deviceinterfaces.

Remote computing device applications may ensure the imaging device isnot being “spoofed,” The remote computing device may be able toauthenticate an imaging device that it is contract with it to ensure anintruder cannot imitate the imaging device to collect networkconfiguration and password information, monitor file/folder structuresof a document management system, or spoof security settings and DSKstatus of the imaging device.

A remote computing device may ensure that the server is not being“spoofed.” The imaging device must be able to authenticate all remotecomputing devices that it is in contact with to ensure that an intruderis not spoofing the remote computing device's IP address. By pretendingto be the remote computing device, an intruder could steal usercredentials, redirect scanned documents, change device settings orfirmware, or bring down the access control system (either to provideaccess to unauthorized users or initiate a denial of service attack forvalid users).

Access control/vend applications may not be compromised when a remotecomputing device is unavailable. When the remote computing device isunavailable, it may not be acceptable to provide open access to thedevice. If the remote computing device is unavailable at startup orbecomes unavailable at anytime (e.g. someone disconnects network cable),the imaging device may immediately be disabled and an error messagedisplayed.

An administrator may be able to adjust a security level based on companyand application requirements. Security requirements can have a largeimpact on the time it takes to develop a remote computing deviceapplication and the resources required to implement the solution. Usersusing some embodiments may range from a small business with one imagingdevice, no IT staff, and a simple scan or print application to a largegovernment office using access control and audit trails to track alldevice activity. The security measures used to protect imaging deviceinterfaces may be adjustable by the administrator to match the targetenvironment.

The imaging device and remote computing device applications may be ableto hand-off user credentials. Users may be prompted to login at multiplepoints throughout a job. For example, an access control application oraccounting application may control total device access, the imagingdevice may have user authentication enabled for Image Send, and adocument management application may require user login before showing afolder list. In many environments, all of these applications will use acommon user database. In some embodiments, it is, therefore, desirablefor the applications to pass user credentials to each other, so thateach one does not have to repeat the authentication process.

Some embodiments of the present invention may be described withreference to FIG. 3. These embodiments comprise an imaging device only,which is configured to interact with a remote computing device, such asa server through a communications link. The imaging device 30 comprisesa user interface 32, which comprises a user input device 34, such as akeypad, one or more buttons, knobs or switches or a touch-screen paneland a display 36, which may comprise user input device 34 in the form ofa touch-screen panel.

Imaging device 30 will typically be capable of performing one or moreimaging functions including, but not limited to, scanning, printing,copying, facsimile transmission (sending and receiving and others.

These embodiments further comprise a communications link 38, which maybe a wired connection (as shown in FIG. 3) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apower line communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 38 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared Data Association (IrDA)connection or some other wireless connection.

The operation of some imaging device embodiments may be explained withreference to FIG. 4. In these embodiments, menu data is received 40 froma remote computing device (not shown in FIG. 3), which is connected tothe imaging device 30 via the communication link 38 through a wired orwireless connection. This menu data is then displayed 42 on the imagingdevice user interface display 36. This display of remote menu data isintended to prompt a user to make an input on the user interface inputdevice 34.

Imaging devices of these embodiments are further configured to acceptinput from a user in response to a display of remote menu data andcommunicate 44 that user input to a remote computing device. In someembodiments, this user input data will be processed by a remotecomputing device. This may comprise running an application on the remotecomputing device. This processing may also comprise accessing andcommunicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured toreceive 46 data resulting from processing the user input data. This maycomprise data generated by an application running on the remotecomputing device in response to the user input. The imaging device mayalso receive data that was stored on a remote computing device, such asa file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, theimaging device 30 may perform 48 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may active or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 46 ofprocessed data.

Some, more specific, imaging device embodiments may be explained withreference to FIG. 5. In these embodiments, the imaging device 30 isconfigured to receive 50 menu data formatted in a markup language from aremote computing device. The communication link by which the menu datais communicated may be established and maintained using a HypertextTransfer Protocol (HTTP). The markup language may comprise terms fromHypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imagingdevice user interface display 36. As in previously describedembodiments, the menu data is typically intended to prompt user input onimaging device user interface 32. Display 52 of the remotely-stored menudata may be accomplished with a browser application that is native tothe imaging device 30.

In these embodiments, the imaging device 30 is further configured toroute 54 user input received though its user interface 32 to a remotecomputing device. The remote computing device that receives the userinput may then run an application or otherwise process the user inputand return the results of the processing to the imaging device 30.Accordingly, the imaging device 30 is further configured to receive 56processed data from a remote computing device. In some embodiments, theimaging device 30 may perform one or more functions in response to thereceipt 56 of processed data.

Some embodiments of the present invention may be explained withreference to FIG. 6. These embodiments comprise a remote computingdevice (RCD) 60, which has a communications link 64. Communications link64 may be a wired connection (as shown in FIG. 6) comprising a networkcable, a Universal Serial Bus (USB) cable, a serial cable, a parallelcable, a powerline communication connection such as a HomePlugconnection or other wired connections. Alternatively, the communicationslink 64 may comprise a wireless connection, such as an IEEE 802.11(b)compliant connection, a Bluetooth connection, an Infrared connection,such as those defined in the Infrared Data Association (IrDA) standardor some other wireless connection. In some embodiments, RCD 60 mayfurther comprise a data storage device 62, which is typically a harddrive, but may also be an optical drive device, such as an array ofcompact disk drives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7.In these embodiments, RCD 60 comprises a processor 72 for processingdata and running programs such as operating systems and applications.RCD 60 may further comprise memory 74, which may be in the form ofRandom Access Memory (RAM) and Read Only Memory (ROM), Generally, anyapplications processed by processor 72 will be loaded into memory 74.RCD 60 may further comprise a network interface 78, which allows RCD 60to communicate with other devices, such as an imaging device 30. In someembodiments, RCD 60 may also comprise a user interface 80, but this isnot required in many embodiments. Storage 62 may be used to storeapplications and data that may be accessed by an imaging device 30 ofembodiments of the present invention. Processor 72, memory 74, storage62, network interface 78 and, optionally, user interface 80 aretypically linked by a system bus 76 to enable data transfer between eachcomponent. Communications link 64 may couple the RCD 60 to other devicesvia network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 maycomprise menu data stored on storage device 62 or in memory 74. Thismenu data may be configured for display on an imaging device userinterface 32. Menu data may be stored in many formats andconfigurations. In some embodiments menu data may take the form of termsexpressed with a markup language. The markup language may comprise termsfrom Hypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages. In these embodiments, menu data may besent 82 through a communications link 64 to an imaging device 30.Accordingly, menu data configured for display on an imaging device isstored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84user input obtained through the user interface 32 of an imaging device30 and transferred to the RCD 60 over communications links 38 & 64. Oncethis input data is received at an RCD 60, the input data may beprocessed 86. This processing 86 may comprise conversion of the data toa new format, execution of commands contained within the data or someother process. Once the input data has been processed 86, the processedoutput may be sent 88 back to the imaging device 30 where the processedoutput may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60may send 90 menu data configured for an imaging device display 36 usinga markup language. The markup language menu data is then received at theimaging, device 30 and displayed to a user, Typically, this will promptthe user to enter an input on the imaging device user interface 32. Thisuser input will then be sent by the imaging device 30 to the RCD 60. TheRCD 60 will then receive 92 the input data prompted by the display ofthe menu data on the imaging device 30. Once received, the input datamay be processed 94 on the RCD 60. Processing may comprise theselection, recordation and/or modification of a form, document or otherdata stored on RCD 60, the authorization of a user identified by theuser input, the translation of a document input by the user, generationof a map or other directions related to user input or some other processor function.

Some embodiments of the present invention may be described withreference to FIGS. 10 & 11. These embodiments comprise at least one RCD60 and a plurality of imaging devices 30 a-30 d. In these embodiments,at least one of the imaging devices 30 a-30 d comprises a user interface32 with a display 36 and user input panel 34 that is integral with thedisplay (i.e., touch-screen) or a separate input unit. RCD 60 isconnected to imaging devices 30 a-30 d by a communications link andnetwork 100 to enable data transmission between RCD 60 and imagingdevices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to atleast one of the imaging devices 30 a-30 d where the menu data isdisplayed on a user interface. Any of Imaging devices 30 a-30 d thatreceive the menu data are configured to accept 112 and transmit 114 userinput to an RCD 60. Once the user input data is received at the RCD, thedata may be processed 116 as discussed in previously describedembodiments. The result of processing 116 may then be sent 118 back toany combination of the imaging devices 30 a-30 d.

In these embodiments, a single RCD 60 may be used to provide processingpower, resources and functionality to a plurality of imaging devices 30a-30 d without reproducing these resources in each imaging device. Insome embodiments, data generated by input on one imaging device 30 a maybe directed to another imaging device 30 d for processed data output orfinal processing.

Some embodiments of the present invention may be described withreference to FIG. 12. In these embodiments, an imaging device (IDev) 120comprises a user interface 124, which is capable of receiving user inputand displaying data to a user. The user interface 124 will typicallycomprise a display, often in the form of a touch panel. The display maybe used to display data to a user. This data may comprise menu data toprompt for a user selection or data entry, such as a user ID andpassword, form selection or some other input. The imaging device 120 hasa communication link 122, which may comprise a typical computer networkconnection, a serial cable or some other wired or wireless communicationlink as described in other embodiments. The communication link 122 mayconnect the imaging device 120 to a remote computing device (RCD) 126 a,126 b, such as a server. The RCD 126 a, 126 b may be used to storedocuments, such as forms, and other data and make that data accessiblefrom the imaging device 120. The RCD 126 a, 126 b may also executeapplications that interact with or receive input from the imaging device120 and its user interface 124. In some embodiments, a database 125 maybe linked to the imaging device 120 and/or an RCD 126 a, 126 b. In someembodiments, on RCD 126 b or database 125 may be connected to an IDev120 over a wide area network such as the internet 128.

Accounting Data Maintenance Embodiments

Some embodiments of the present invention comprise methods and systemsfor maintaining imaging device (IDev) accounting data when a primaryserver becomes unavailable. These embodiments comprise a lightweightaccounting backup server (LABS) application capable of running on otherservers or practically any networked computing device.

In a typical imaging device system, IDevs are placed under accountingcontrol, meaning that they are connected to an application running on aserver that is tasked with recording the device's activity. In additionto recording device activity, such as the number of copies made by eachindividual or on each account, a server application may also enable anddisable IDev functions in relation to a user's credentials. This is donefor the purpose of being able to charge accounts or individuals for theuse of the IDev. In a typical system, when an accounting applicationfails or becomes temporarily unavailable, the IDev may be entirelydisabled, preventing users from using the IDev to accomplish theirtasks. The IDev may also remain enabled but with no record of the IDevusage. Both of these alternatives are unacceptable in a typicalcommercial setting.

Embodiments of the present invention comprise methods and systems thathave the capability to continue providing accounting control over animaging device when the main accounting server is down. In theseembodiments, this is achieved with a lightweight accounting backupserver (LABS) running on one or more personal computers in the system.When the primary accounting server returns to service, it may query theLABS for their accounting data and then update the primary IDev activitylog.

Some embodiments of the present invention may comprise devices with alist of lightweight accounting back-up servers (LABS) that are availableto that device. This information may be in the form of a uniformresource locator (URL) pointing to the LABS application's web serverentry points. This list can be managed manually or can be populated bysome form of discovery mechanism. When the primary server becomesdisabled the IDev may attempt to connect to the first LABS on the listand may subsequently continue to connect to each consecutive LABS on thelist until it succeeds. Once this occurs, the LABS may take over theaccounting control of the IDev.

In some embodiments, the LABS may not fully implement the same set offeatures that the primary accounting server (PAS) applicationimplements. For example, and not by way of limitation, the LABS maycomprise only departmental information for specific departments thattypically use a particular IDev rather than have whole enterprise dataas in the primary accounting server (PAS). A LABS may implement all thefunction of a PAS, or it may implement a limited subset. In someembodiments, the LABS may only implement user login and click countfunctions. In these embodiments, some IDev functions may be unavailableto a user.

When the primary accounting server comes back online a message may besent to the IDev indicating that the PAS is back in service. The IDevmay then notify any LABS and instruct them to transfer any temporaryIDev accounting log (TIAL) data they have recorded to the primaryserver. Finally, the IDev may return to sending accounting data to theprimary accounting server until such time as the primary server becomesunavailable again.

In some embodiments, the PAS may communicate directly with a LABS whenrequesting TIAL data and when receiving TIAL data from the LABS.However, in some embodiments, direct LABS to PAS communication may notbe used and communication may be routed through the IDev.

Some embodiments of the present invention may comprise an imaging device(IDev) in communication with one or more additional IDevs and one ormore remote computing devices (RCDs) running LABS applications. TheseIDevs may also have communication with a primary accounting server.

Some embodiments of the present invention may be described withreference to FIG. 13A. These embodiments may comprise one or morenetworked computing devices 135A-135G & 132A-132D which are linked withone or more accounting-controlled Imaging Devices (IDev) 131A-131Dthrough a communication network 134. These IDevs 131A-131D and computingdevices 135A-135G & 132A-132D may also be linked with a PrimaryAccounting Server (PAS) 133. The PAS may store IDev activity data andaccounting data received from the IDevs 131A-131D.

Some of the networked computing devices 135A-135G & 132A-132D on thenetwork 134 also function as LABS 132A-132D. These LABS 132A-132D areapplications running on computing devices that provide some kind ofaccounting control and/or IDev activity recording functions. An LABS132A-132D may be part of a computing device that has some other primaryfunction. In some embodiments, a LABS 132A-132D may be part of a typicalclient computing device or workstation that is used for word processing,drafting or some other primary application. The LABS application may runin the background and be transparent to a primary computing device user.132A-132D

In the event that the primary accounting server (PAS) 133 goes offline,the IDevs 131A-131D may send their accounting data to the lightweightaccounting backup servers (LABS) 132A-132D which may temporarily storethe data until the primary accounting server (PAS) 133 comes backonline.

Some embodiments of the present invention may also be described withreference to FIG. 13B. In these embodiments, a system may comprise acomputing device 136 in communication with an imaging device (IDev) 137and a primary accounting server 138. In these embodiments, the computingdevice comprises a component that functions as a lightweight accountingback-up server (LABS) 139. The components may be connected with anetwork 134, such as a wired or a wireless network. The components ofthese embodiments function as in other embodiments, but the scale of thenetwork is much smaller.

Some embodiments of the present invention may be described withreference to FIG. 14A. These embodiments comprise anaccounting-controlled IDev that performs IDev functions for a user. TheIDev may also provide access to remote applications to a user.Typically, a user will log on to the system by providing account dataand user credentials and the IDev and/or associated local or remoteapplications will authenticate the user credentials and allow access tothe system in relation to the user's account. When the user accessesIDev functions, local applications and/or remote applications, the IDevmay monitor this activity and report the activity to an accountingserver. This report may be made to a primary accounting server (PAS) orto a lightweight accounting back-up server (LABS) depending on thecurrent status of the network and the servers.

When all servers, devices and network components are functioningproperly (the PAS is available to the IDev), the IDev may determine 140that a PAS is available and send 141 activity data to a primaryaccounting server (PAS). Alternatively, a message may be sent using anacknowledgement process to determine PAS availability. When a PAS is notavailable 142, the IDev may access 143 a list of LABS from the primaryserver and determine the availability 144 of a LABS on that list. When aLABS is determined to be available 145, the IDev may activity data 146to that LABS. The LABS may then keep a temporary IDev activity log(TIAL) for that IDev. If the LABS is not available 145, the IDev mayprogress down the list to another LABS and determine the availability144 of each LABS until it finds an available LABS. The IDev may thensend 147 its activity data to the available LABS. In some embodiments,this process may be followed for each activity message sent by the IDev.In other embodiments, once an available LABS is found, that LABS may bedesignated as the current accounting server (CAS) and all activity datawill be sent to that server until a change in availability.

In some embodiments of the present invention, multiple LABS may be usedby a single IDev or multiple IDevs. In some embodiments, regional LABSmay be assigned to different regions of the area served by the PAS. Whena PAS becomes unavailable, IDevs may report to regional LABS dependingon their geographic location, account status, user credentials, IDevtype or some other regional differentiator. Each region may have aseries of LABS. In some embodiments, a regional LABS may have otherregional LABS as back-up LABS listed in it's IDevs' lists.

Some embodiments of the present invention may be described withreference to FIG. 14B. The description of these embodiments illustratesa data recovery process that occurs when an unavailable PAS becomeavailable. In these embodiments, a PAS may send out a recovery messagewhen it becomes available 148. When the IDevs receive the recoverymessage, they may re-commence 149 sending activity data to the PAS. Insome embodiments, the LABS may also receive the recovery message and, inresponse, the LABS may send their temporary IDev activity logs (TIALs)to the PAS. In some embodiments, wherein the LABS does not receive therecovery message, the IDev may respond to the recovery message bysending 150 a message to the LABS instructing the LABS to send its TIALto the PAS. Once the PAS has received TIAL data, the PAS may update 151its primary IDev activity log (PIAL) with the temporary data loggedwhile the PAS was unavailable.

Some embodiments of the present invention may be described withreference to FIG. 15. These embodiments comprise an IDev that is capableof sending messages and activity data to a primary accounting server(PAS) and to a LABS. In some embodiments, the PAS and the LABS may alsocommunicate directly. In these embodiments, when a PAS becomesunavailable, the IDev is no longer able to send activity data to thePAS. This may be detected by a message acknowledgement process, bypinging the PAS or by many other methods.

When the PAS become unavailable 154, the IDev may access 155 its LABSlist to determine the address of an alternate LABS. The IDev may thendetermine the availability of a first LABS on the list. In someembodiments, this may be done by sending 156 a message to the first LABSon the list according to a send and acknowledge process. If anacknowledgement is received from the first LABS 157, the IDev may send159 its activity data to the first LABS, which will then compile thatdata into a TIAL. If the first LABS does acknowledge 157 the message,the IDev may send a message to the next LABS on the list 158 andcontinue the process until a LABS acknowledges the process, receives theactivity data and compiles a TIAL.

Some embodiments of the present invention, illustrated in FIG. 16,comprise an IDev capable of communicating with a LABS. In theseembodiments, these elements follow an exemplary process for maintainingactivity data during a PAS failure followed by a LABS failure. In thisexemplary process, an IDev sends activity data to a LABS, which compilesa TIAL. In these embodiments a send and acknowledge process is used,however, in alternative embodiments the availability of a LABS may bedetermine by other methods. An IDev may send 162 a message to an LABS inexpectation of an acknowledgement (ACK). If an ACK is received 164, theIDev will continue sending 168 activity data to the LABS. If an ACK isnot received 164, the IDev may access its LABS list and send a message166 to the next LABS on the list in expectation of an ACK. This processwill continue until the IDev's message receives an ACK at which pointthe IDev will send its activity data to the acknowledged LABS.

Some embodiments of the present invention, illustrated in FIG. 17,comprise a method and/or system for recovering data to a primaryaccounting server (PAS) after a period of unavailability. In theseembodiments, the PAS comes on-line 170 by connecting to the network withfull functionality. The PAS then sends a recovery message 172 that maybe received by any IDevs on the network as well as other devices. Whenan IDev receives the recovery message, the IDev may respond byrecommencing the sending of its activity data 173 to the PAS. In someembodiments the IDev may respond to the recovery message by sending amessage to the LABS instructing the LABS to send TIAL data to the PAS.The PAS will then receive 176 the TIAL data and update 178 its primaryIDev activity log (PIAL) with the TIAL data.

Some embodiments of the present invention, illustrated in FIG. 18,comprise a method and/or system for recovering data to a primaryaccounting server (PAS) after a period of unavailability. In theseembodiments, the PAS comes on-line 180 by connecting to the network withfull functionality. The PAS then sends a recovery message 182 that maybe received by any IDevs on the network as well as other devices, suchas LABSs. When an IDev receives the recovery message, the IDev mayrespond by recommencing the sending of its activity data 183 to the PAS.In some embodiments a LABS may also respond to the recovery message bysending 184 any TIAL data the LABS has logged to the PAS. In someembodiments, the TIAL data may be sent in response to a specific request184. The PAS may then receive 186 the TIAL data and update 188 itsprimary IDev activity log (PIAL) with the TIAL data.

The terms and expressions which have been employed in the forgoingspecification are used therein as terms of description and not oflimitation, and there is no intention in the use of such terms andexpressions of excluding equivalence of the features shown and describedor portions thereof, it being recognized that the scope of the inventionis defined and limited only by the claims which follow.

1. A system for maintaining imaging device (IDev) accounting data, saidsystem comprising: a) a primary accounting server (PAS), said PAScomprising; i) a PAS sender for sending messages to an imaging device(IDev) and to a lightweight accounting back-up server (LABS); ii) a PASreceiver for receiving messages from said IDev; iii) an updater forupdating a (primary IDev activity log (PIAL). b) an imaging device(IDev), said IDev comprising; i) an IDev sender for sending messages;ii) an IDev receiver for receiving messages from said Primary server andsaid LABS; and c) at least one LABS in communication with said IDev,said LABS comprising; i) a LABS receiver for receiving messages and datafrom said IDev and from said PAS; and ii) a LABS sender for sendingmessages to said IDev and to said PAS; d) wherein said IDev sends arecord of its activity to said PAS when said PAS is available and saidPAS maintains a primary IDev activity log (PIAL) when said PAS isavailable; e) wherein said IDev sends a record of its activity to saidLABS when said PAS is not available and said LABs maintains a temporaryIDev activity log (TIAL) when said PAS is not available; and f) whereinsaid PAS updates said PIAL with said TIAL data after a period ofunavailability.
 2. A system as described in claim 1 wherein said LABS isan application running on a remote computing device in communicationwith said IDev and said PAS.
 3. A system as described in claim 1 whereinsaid IDev further comprises a list of said at least one LABS.
 4. Asystem as described in claim 1 wherein said at least one LABS comprisesa plurality of LABS accessible in a sequential order thereby forming amultiple redundant back-up server system.
 5. A system as described inclaim 1 wherein PAS sends an update message to said IDev after a periodof unavailability and, in response to said update message, said IDevrenews sending a record of its activity to said PAS, requests said TIALdata from said LABS sends said TIAL data to said PAS.
 6. A system asdescribed in claim 1 wherein said PAS sends an update message to saidLABS after a period of unavailability and, in response to said updatemessage, said LABS sends said TIAL data to said PAS.
 7. A system asdescribed in claim 1 further comprising an accounting application forreporting said PIAL data to a user.